Skip to content

Conversation

adamchainz
Copy link
Contributor

Why:

Pull requests always come with a Checks tab, at least nowadays. Perhaps some change to promote GitHub Actions made the tab always appear.

I verified this by creating an empty repository and performing the minimum of moves to make a PR. It had a Checks tab:

Screen Shot 2025-09-27 at 00 04 44

What's being changed (if available, include any code snippets, screenshots, or gifs):

Removing one clause.

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the review environment.

@Copilot Copilot AI review requested due to automatic review settings September 26, 2025 23:06
Copy link

welcome bot commented Sep 26, 2025

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR removes outdated conditional language about the Checks tab availability in pull requests. The change reflects that pull requests now always display a Checks tab, regardless of whether checks are configured.

  • Simplifies documentation by removing an unnecessary conditional clause
  • Updates content to match current GitHub UI behavior where the Checks tab is always present

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Sep 26, 2025
Copy link
Contributor

github-actions bot commented Sep 26, 2025

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md fpt
ghec
ghes@ 3.17 3.16 3.15 3.14
fpt
ghec
ghes@ 3.17 3.16 3.15 3.14

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@Sharra-writes
Copy link
Contributor

@adamchainz Thanks for updating the wording! I'll get this approved.

@Sharra-writes Sharra-writes added this pull request to the merge queue Sep 29, 2025
Merged via the queue into github:main with commit 7a90f72 Sep 29, 2025
40 checks passed
Copy link
Contributor

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants